[Chore] Use fictional placeholder data in test fixtures and dev examples - #192
Merged
mrubens merged 2 commits intoJul 11, 2026
Merged
Conversation
… with fictional values
Contributor
Author
|
No new code issues found — the latest commit resolves both previously flagged consistency issues, and the affected tests pass. See task
|
… harness examples
mrubens
marked this pull request as ready for review
July 11, 2026 15:16
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 11, 2026 15:16
This was referenced Jul 11, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Standardizes test fixtures, eval datasets, and dev-setup examples on clearly fictional placeholder data:
example.slack.comwith placeholder channel/user IDs (C0EXAMPLE01/U0EXAMPLE01) and generic message text.R_PUBLIC_URLsetup error inapps/dev/src/services/env.tssuggestshttps://your-ngrok-domain.ngrok.app, matching.env.local.example.roomote.*tenant domain shape is kept because the ADO regression tests specifically assert that humans in aroomote.*tenant are not matched as Roomote's own bot identity.No production logic changes: outside tests and eval data, only a code comment and an error-message example string are touched.
How it was tested
@roomote/api,@roomote/dev,@roomote/web,@roomote/worker,@roomote/ado,@roomote/communication,@roomote/sdk,@roomote/slack, and@roomote/cloud-agents— all pass.pnpm lintandpnpm check-typespass.Checklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locallypnpm changeset(not needed: test-fixture and dev-example text only)